Skip to content

Avoid fetching dereferenced segments in server-side #414

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: development
Choose a base branch
from

Conversation

EmilianoSanchez
Copy link
Contributor

@EmilianoSanchez EmilianoSanchez commented May 30, 2025

JavaScript commons library

What did you accomplish?

Avoid fetching dereferenced segments in server-side by iterating FF (and RBS) definitions on each update to compute the current set of used segments. CONS: requires iterating all FFs and RBSegment definitions per segmentChangesUpdater call.

Other approaches:

  • Previous one: keep track of used segments, adding them to a set. CONS: we cannot know what segments are dereferenced.
  • Track used segment counts, as we do with traffic types. CONS: more complex and keys required for Redis/Pluggable

How do we test the changes introduced in this PR?

Extra Notes

Possible approaches:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant